top of page

Only available for Logged-in member. Please login or register to access this information.

Or use the Temporary User that we have provided to you via email.

expiry time ​

WSSFCEX-GHC

Manual for WSLRWEX-G | FW7

Obsolete

Replaced by

Replaced by

Item codes
FW Released Date
Changes Information
WSLRW-G4-CL2-20-01; WSLRW-G4-CO-200-01; WSLRW-G4-H2S-50-01; WSLRW-G4-NH3-100-01; WSLRW-G4F-CL2-20-01; WSLRW-G4F-CO-200-01; WSLRW-G4F-H2S-50-01; WSLRW-G4F-NH3-100-01; WSLRWEX-G-H2S-100; WSLRWEX-G-O2-30-HH
26/01/2024
1.Add LNS_CHECK message with message type: ConfirmedDataUp.; 2.Add password requirement for some parameters when writing with offline tool.; 3.Add low alarm and RANGE_FACTOR_INDEX.; 4.Add MODULE_POWER_MODE: 0 => For G4 (NH3, H2S, CL2), 1 => For O2; 5. Add configurable unit.; 6.Add num of sample.; 7.Add Response time for sensor O2

1
QUICK INSTALLATION GUIDE

1.1 Introduction

WSLRWEX-G is an Ex d approved LoRaWAN electrochemical-type gas sensor with a high sensitivity to low concentrations of detected gas, high selectivity, and a stable baseline. The device supports different types of gas such as CO, NO, NO₂, H₂S, NH₃, O₂, O₃, SO₂, Cl₂, HCHO... The device is used in Hazardous Zone 1-2. With Ultra-low-power design and smart firmware allow the complete Wireless and Sensor package to run on a single battery for 5 years or more with 15 minutes update. It supports global frequency bands EU868, IN865, RU864, KR920, AS923, AS923-2, AU915, US915. The sensor can work perfectly with any LoRaWAN Gateway and any Network Server on the market.

How the sensor connect to system?

Below is the LoRaWAN system architecture


System components:

  1. The end nodes are LoRaWAN Sensors or Actuators;

  2. The Gateways are LoRaWAN Gateway or Base Station;

  3. The Network Server can be SAAS or On-premise server;

  4. The Application Server is the destination software users want to utilize the data from/ to LoRaWAN sensors/ actuators.


How to set up the LoRaWAN system? Please follow these steps:

  1. Adding the Gateways to a Network server. Please refer to the manual of Gateway and Network Server software;

  2. Adding the End nodes to the Network Server;

  3. Configure the callback or data forwarding from the Network Server to the Application Software by MQTT or HTTPS. Please refer to the manual of the Network Server.

  4. Once the payload is on the Application server, decode data from Payload. Please check Section 1.9 for the Payload document.

1.2 Application Notes

For Applications

Gas Leakage Detection, Ambient Air Quality Monitor, Indoor Air Quality Monitor

Notes

- Select the suitable sensor range to get the highest accuracy v.s sensor life. Please consult our engineers. Electrochemical sensors need to be calibrated regularly (6-12 months), depending on actual operating conditions.

- Check carefully the working temperature and humidity of the application. Use the Rain-guard of Splash-guard for outdoor installation or where water jets exist.

1.3 When does device send Uplink messages?

The device will send uplink messages in the following cases:


Case 1: After power-up in the 60s, the device will send the first message called START_UP. The payload will tell the user the HW version, FW version, and current configuration of the device.


Case 2: Then, in every interval time (pre-configured), for example, 10 minutes, it will send the message called CYCLIC_DATA. The payload will tell the user the following data like measured values, battery level, and alarm status...

To change the cycle of data sending, you can change the value of the parameter: CYCLIC_DATA_PERIOD.


Case 3: If ALARM_ENABLED=1, the device will send ALARM message immediately when device switches from Normal state to Alarm state. It will repeat sending ALARM messages in predefined ALARM_PERIOD time interval if the Alarm state still exist.


Case 4: During the commissioning, testing, or calibration sensor, the user can force the device to send the uplink message to get the data immediately. This message is called FORCE_DATA. The payload will provide data like raw measured value, scaled measured values, battery level, and alarm status... It can be forced by applying the magnet key on the reed switch in 1s.


Case 5: If users want to change the configuration immediately, they don't need to wait until the next cyclic data-sending message; instead, they can force the device to send a special uplink message so that the device can get the new downlink message. This uplink message is named PARAMETERS_UPDATE. It can be forced by applying the magnet key in more than 5s.


Case 6: In every interval time (pre-configured), for example, 24 hours, it will send the message called HEARTBEAT. The payload will tell the user the following data like hardware version, firmware version, current sensor configuration.


Case 7: If LNS_CHECK_MODE =1, it will send the confirmed uplink message called LNS_CHECK every 24 hours. This confirmed uplink message is a message where a LoRaWAN device is requesting a LoRaWAN network to confirm the reception of its message. If the device receives no confirmation message from LoraWAN network server, it will re-send the LNS_CHECK message every hour during 3 hours. After 4th hour, if the device still receives no confirmation messsage, it will reset itself to join the network server. The LNS_CHECK payload will tell the user the following data like hardware version, firmware version, current sensor configuration.

1.4 Default Configuration

This Ex d approved G gas sensor module has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Please check the Payload document for more information

1.5 Battery/ Power Supply

  • Use 01 x C-size battery 3.6V LiSOCl2 with 7700mAh;

  • Recommend to use SAFT LS26500 or equivalent from Tadiran.






1.6 What's in the Package?



1.7 Guide for Quick Test

With the default configuration, the device can be connected quickly to the Network Server by the following steps.


Step 1: Prepare the values of communication settings

Frequency zone: Most of the sensor was configured the frequency zone to suit customer application before delivery

DevEUI: Get the DevEUI on the product nameplate

AppEUI Default value: 010203040506070809

AppKey Default value: 0102030405060708090A0B0C0D0E0F10

Activation Mode: OTAA with local join server

Network Mode: Public

LoraWAN Protocol: version1.0.3

Class: A for sensor; C for actuator


If current basic common settings do not match with your region, network server/application, follow below instruction to change them as below:





For changing other settings, please refer to Section 3.2 Sensor configuration to change the other settings


Step 2: Register the device on the LoRaWAN network server

Input the above settings on your device registration page of the network server.


Note: Different network server software will have different device registration processes. Please refer to the manual of the network server software used for more details.


Please visit the below Section 1.10 to get the instructions for adding the LoRaWAN sensors to some common network servers such as Actility, TTN...


Step 3: Install the batteries to the device OR do power wiring and supply external power to the device if applicable

Please refer to Section 1.5 as above for instructions on battery installation OR for instructions to do power wiring and supply external power to the the device if applicable

After installing the battery in 60 seconds, the first data packet will be sent to the LoRaWAN gateway. After receiving the first data packet, the time of another packet depends on the value of the parameter: cycle_send_data. Additionally, you can use a magnet key to touch the magnetic switch point on the housing within 1 second to initiate force packet of the device to send data instantly and the LEDs on the housing will be lit with SKY BLUE color.


Step 4: Decode the payload of receiving package

Please refer to Section 1.9 Payload Document and Configuration Tables for details of decoding the receiving packet to get the measured values.

If the device has local display, measured values are shown on the local display

1.8 Installation

Dimension Drawings and Installation Gallery (Photos and Videos)

Please follow the checklist below for a successful installation:

​

1. Have you studied the dimensions of the device as above drawings?
 

2. Have you tested and make sure the device have been connected successfully as Section "1.7 Guide for Quick Test" above?
 

3. Have the device been configured properly as per Section 3.2 below?
 

4. Have the device been calibrated or validated as per Section 3.3 below?
 

5. Then you can start to install the device at site. Please check the following Installation Notes for Sensor Part (if available) before installation.

Installation Notes for Sensor Part (if available)

Notes: Avoid the place with humidity higher than 90% RH all the time (a short time in 2-3 days is acceptable)* if the Sensor is intended to install outdoors, please use a rain guard to protect the sensor from rain and direct sunlight. Please contact us to buy this accessory.


  • Place the sensor in the area to monitor the target gas concentration. Please always check the gas molecular weight vs. the air.

  • For example, NH₃ gas has a lighter weight than air, so the sensor must be placed at a height higher than the source of NH₃ leakage. Normally, the sensor will be mounted at a height of 1.6m from the ground.

  • For NH₃ odor detection in the toilet, users can place the sensor from 1.6m on the wall or on the ceiling with a height ≤ 2.6m


Note for Outdoor installation: For outdoor installation, please use the Rain guard to protect the sensor from raindrops or snowflakes. Please find below the steps of installation of a typical Rain-guard.


Step 1. Prepare the rain guard


Step 2. Insert the rain guard into the sensor filter and tighten the locking screws

  • Insert the Rain guard from the bottom up to the position with the red color mark;

  • Tighten the 02 screws on both sides of the Rain guard to secure it in place.


Installation Guide for Main Device

Note: Do not open the device or replacing battery during installation at site (hazardous area Zone 0, 1, 2)


Check Location for the best RF Signal

Make sure the site is good enough for RF signal transmission.


Tip: To maximize the transmission distance, the ideal condition is Line-of-sight (LOS) between the sensor and the Gateway. In real life, there may be no LOS condition. However, the sensor still communicates with the Gateway, but the distance will be reduced significantly.


DO NOT install the wireless sensor or its antenna inside a completed metallic box or housing because the RF signal can not pass through the metallic wall. The housing is made from Non-metallic materials like plastic, glass, wood, leather, concrete, and cement…is acceptable.


Mounting

Mount the sensor onto a wall by two screws as below picture:


1.9 Payload Document and Configuration Tables

Please click below button for:
 

  • Payload decoding of Uplink messages;

  • Payload encoding of Downlink messages;

  • Configuration Tables of device.

​​

Note:

If the content of below web payload, memory map, and sample decoder could not be copied, please install the extension of "Enable Copy Paste - E.C.P" for Microsoft Edge and for Google Chrome.

1.10 How to connect device to Back-end/ Network Server/ Coordinator

Please find below the examples of adding Daviteq's LoRaWAN sensor to the following Network servers:

  • ThingPark Community (of Actility);

  • Things Stack (of The Things Network).


You can use the similar methods to add LoRaWAN sensors to other Network Server.


1. THINGPARK COMMUNITY (ACTILITY) NETWORK SERVER
1.1. Example to add the Tektelic LoraWAN gateway Model T0005204 to ThingPark Enterprise SaaS Community

1. Log in to your ThingPark Enterprise account via the link: https://community.thingpark.io/tpe/

2. Browse on the left panel to Base Stations, click the drop-down menu, then click Create.



3. Select the base station’s Tektelic.

※ If you do not find the Tektelic, click View More Manufacturers.


4. On the following screen, select the Model: Micro 8-channels from the drop-down list.


5. Fill the form as below table:


Input exactly as above Input field column, except Name field is user-defined and is different from the existing base station name on the network server.

After filling the registration form, click CREATE to complete adding the base station to the network server.


1.2. Add Daviteq's LoRaWAN devices to ThingPark Enterprise SaaS Community

ThingPark Enterprise supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server that is programmed at the factory.


Manual provisioning of OTAA devices using a local Join Server. To learn more, see Activation modes.


1. At left panel of the screen of the Thingpark GUI, click Devices > Create from the dashboard.


2. Select the Generic supported by your device on your screen.


3. Select the Model of LoRanWAN 1.0.3 revA - class A with correct frequency plan


4. Fill the form as below table:


In addition to filling out the form, the option to select the connection between ThingPark and Daviteq application (Globiots).


After filling out the registration form, please click CREATE to add devices to the network server.


1.3. Send a downlink frame from Thingpark Network Server to the device

Follow the below steps to send the downlink frame from Thingpark Network Server to the device:

This functionality is active only when a connection is associated to the device (one of the color codes with a green bullet).


1. Navigate to the left panel, click the Devices' drop-down menu, then click List.


2. Browse the right side in the Devices, click the icon of the device and click Send Downlink.


3. Input the downlink code to the Payload field and input 1 to the Port field, and then click Validate.


2. THINGS STACK (THE THINGS NETWORK) NETWORK SERVER
2.1. Add Sentrius LoraWAN gateway (Model RG19) to The things Stack network server

1. Log in to you’re The Things Stack account


2. Click the tab Gateways, click Add gateway button


3. Fill out the form as below table:


Input exactly as above Input column, except the Gateway Name field and the Gateway ID field is user-defined. It is different from the existing gateway name and gateway ID on the network server.

After filling the registration form, click Create gateway to complete adding the base station to the network server.


2.2. Add Daviteq's LoRaWAN device to The Things Stack network server

The Things Stack supports all Classes of LoRaWAN® devices. By default, the sensor supports Over-the-Air Activation (OTAA) with a local Join Server programmed at the factory.


1. Browse on the top panel, click the tab Application, and click Add application button to create an application


2. Fill in the information fields as user-defined, then select Create application


3. After the application is created successfully, select Add end device to register end device (LoRaWAN sensor)


4. Fill out the form as below table:


After filling out the registration form, please click the Register end device button to add the device to the network server.


 

1. Select the device to send downlink


2. Input 1 to the FPort and input the downlink data in the payload field, and then tick Confirmed downlink and click Schedule downlink.


2
MAINTENANCE

2.1 Troubleshooting

Please find below steps to identify the problems from Communication Part or Sensor Part:


  • If the device cannot connect to the Gateway or System or Co-ordinator at the first time, it is the Communication Problem;


  • If the device status like battery, RSSI level, data status or other communication is normal, but the measured values are not updated or wrong, it would be the problems of Sensor part;


  • If the data coming to gateway, system or co-ordinator is not frequently as expected, the problem would be Communication.


Please refer below the troubleshooting guide for Communication and Sensor Part.

Troubleshooting for Communication



Troubleshooting for Sensor Part (if available)

1. The measured value is not within the expected value

  • The sensor is drifted over time: Re-calibrate the sensor

  • The sensor was in a high humidity environment (> 90% RH) for more than 03 days continuously: Place the sensor in low humidity for its recovery. It may take up to 30 days to recover. If the sensor cannot recover after 30 days, please replace the new sensor module.


2. The measured value is always zero or near zero

  • The sensor module was removed: Please check the sensor;

  • The sensor is at the end of its life: Replace the sensor module.


3- HW_Error = 1

  • Loosed connection of sensor module and wireless transmitter: Check the internal wiring.

  • The measuring module got a problem: Please consult the manufacturer for a warranty or replacement.

2.2 Maintenance

Maintenance for Main device

There is no requirement for maintenance of the hardware of LoRaWAN device except

1. The battery needs to be replaced. Please check the battery status via uplink messages;


Note: When the battery indicator shows only one bar (or 10% remaining capacity), please arrange to replace the battery with a new one as soon as possible. If not, the battery will drain completely, and the resulting chemical leakage can cause severe problems with the electronic circuit board.


2. Sensor, please refer to the maintenance section of the sensor document.

Maintenance for Sensor part (if available)

Cleaning the Filter: Approx. 3-12 months

Check and clean the filter every few months, depending on the environment. Clean the filter with warm water and soap, then use compressed air to purge it from the inside out.


Re-calibration: Approx. 6-12 months

The gas sensor may be drifting over time. Please check the sensor specification to identify the interval time for the re-calibration sensor.


Sensor replacement: Approx. 1-2 years

Replace the new sensor module after 1-2 years of operation (please check the sensor specification of each gas type). The actual time for replacement depends on the sensitivity of the sensor. Please see below instructions of sensor replacement.


Sensor replacement instructions:


Please remove the batteries before doing the following steps.


Step 1. Unscrew the gas housing


Step 2. Remove the filter housing


Step 3. Unplug gently the sensor module


Step 4. Plug gently and firmly the new sensor module into the PCB


Step 5. Insert the batteries and start calibration as per Section 3


Step 6. Place the filter cover back and screw to lock


3
ADVANCED GUIDE

3.1 Principle of Operation

Principle of Operation for device WSLRW-G4 | FW7

Daviteq LoraWAN 4-Seri Gas (G4) Sensor comprises 02 parts linked internally:

• The Daviteq LoraWAN wireless transmitter;

• The Daviteq 4-Seri Gas (G4) module


What are the primary output values?

• RAW VALUE: Raw value from the sensor. This parameter equals RAW_VALUE in the uplink payload

• SCALED VALUE: Gas level, unit of % for O2 gas and unit of ppm for other gases, scaled value, used for alarm. The scaled value is calculated (scaled/calibrated) from the raw value:

SCALED_VALUE= (CONSTANT_A x RAW_VALUE) + CONSTANT_B; Where CONSTANT_A, CONSTANT_B are configured in the sensor memory map. This parameter equals SCALED_VALUE_X_RANGE_FACTOR in the uplink payload divided by RANGE_FACTOR

• MIN SCALED VALUE: Minimum value of SCALED_VALUE during sending cycle. This parameter equals MIN_SCALED_VALUE_X_RANGE_FACTOR in the uplink payload divided by RANGE_FACTOR

• AVG SCALED VALUE: Average value of SCALED_VALUE during sending cycle. This parameter equals AVG_SCALED_VALUE_X_RANGE_FACTOR in the uplink payload divided by RANGE_FACTOR

• MAX SCALED VALUE: Maximum value of SCALED_VALUE during sending cycle. This parameter equals MAX_SCALED_VALUE_X_RANGE_FACTOR in the uplink payload divided by RANGE_FACTOR

• ALARM DURATION: Alarm duration in hours. This parameter equals ALARM_DURATION in the uplink payload.

• EXTREME SCALED VALUE: Extreme value of SCALED_VALUE during alarm period. Extreme value is max value for high alarm and too high alarm. Extreme value is min value for low alarm. This parameter equals EXTREME_SCALED_VALUE_X_RANGE_FACTOR in the uplink payload divided by RANGE_FACTOR

• RANGE FACTOR INDEX: Index of RANGE_FACTOR to calculate the RANGE_FACTOR. This index based on sensor maximum range of the sensor:

* Max range 0-100 unit => RANGE_FACTOR_INDEX=0 and RANGE_FACTOR=100;

* Max range 101-1000 unit => RANGE_FACTOR_INDEX=1 and RANGE_FACTOR = 10;

*Max range 1001-10000 unit => RANGE_FACTOR_INDEX=2 and RANGE_FACTOR=1

*Max range 10001-100000 unit => RANGE_FACTOR_INDEX=3 and RANGE_FACTOR=0.1

This parameter equals RANGE_FACTOR_INDEX in the uplink payload



What are the secondary output values?

Below output values are useful for device maintenance and troubleshooting.

• Battery level (%): the remaining capacity of the battery. The parameter in the payload is BATTERY_LEVEL.

Note: To get the accurate battery level indication, please configure the battery type by Downlink type 5 or via offline cable to the parameter name BATTERY_TYPE.The default type is Primary battery. For Solar powered version, please configure to Rechargeable battery type.

• Number of consecutive Alarm: The number of consecutive alarm message. This parameter in the payload is TENTATIVE. TENTATIVE will be reset to 0 when previous message is alarm and current message is cyclic.

• Alarm: alarm status of the device. The parameter in the payload is ALERT_STATUS

• Sensor error: sensor working properly or not and this parameter in the payload is SENSOR_COM_ERROR

• Sensor current configurations: current main settings of the sensor and this parameter in the payload is CURRENT_CONFIGURATION

• Sensor hardware version: hardware version of the sensor and this parameter in the payload is HW_VERSION

• Sensor firmware version: firmware version of the sensor and this parameter in the payload is FW_VERSION


Principle of operation

Most of the time, the device will be in sleep mode. When the timer reaches the Measure_Period (for example, 30 minutes), it will wake up the device to start the measurement.

*** This Measure_Period will affect the energy consumption of the device.

The measurement will take a certain time to finish; it can take milliseconds or seconds to finish the measurement. This measurement time depends on sensor type, required accuracy, and other factors. Shorter measurement time, lower energy consumption, and longer battery life.

After finishing the measurement cycle, the device can read all the measured parameters.

Main parameter for alarm is SCALED VALUE


For High Alarm and High High Alarm


If parameter ALARM_ENABLE = 1

Then the device will compare the main parameter with High High Alarm Setpoint and High Alarm Setpoint, together with Hysteresis to define the state of the device is No_Alarm or Hi_Alarm or HiHi_Alarm.


Hysteresis value is to avoid the flickering status (Alarm/No-Alarm toggling quickly) when the measured value close to alarm threshold. The hysteresis is zero for this sensor.


  • If an axis is in Blue color area of above graph, the device is in Normal or No_Alarm state;

  • If an axis is in Red color area, the device is in HiHi Alarm state (Alarm 2);

  • None of above 02 states, the device will be in Hi Alarm state (Alarm 1).


How the device send uplink message base on above states?


If Device state is changed from No_Alarm to Hi Alarm or HiHi Alarm, it will send alarm message immediately. Please check the below picture to understand the operation flow when finishing the measurement cycle:


Once alarm happened and send the first alarm message, the device will send the next alarm message in the Alarm_Period if the device is still in Alarm states (Hi Alarm or HiHi Alarm). Please check below picture to understand the operation flow when the Alarm timer reaches the Alarm_Period. Alarm_Period is fixed value of 10 minutes.



For High Alarm and Low Alarm


If parameter ALARM_ENABLE = 1

Then the device will compare the main parameter with the Low Alarm Setpoint, High Alarm Setpoint and Hysterisis. For this device, Hysteresis equal zero.


After comparison, the devices will have 03 statuses:

  • No_Alarm;

  • Low_Alarm

  • High_Alam.


How the device send uplink message base on above 03 states?

If Device state is No_Alarm, it will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;


If Device state is changed from No_Alarm to Low_Alarm or Hi_Alarm, it will send alarm message immediately. Please check the below picture to understand the operation flow when finishing the measurement cycle:


Once alarm happened and send the first alarm message, the device will send the next alarm message in the Alarm_Period if the device is still in Alarm states (Low_Alarm or High_Alarm). Please check below picture to understand the operation flow when the Alarm timer reaches the Alarm_Period. Alarm_Period is fixed value of 10 minutes.


If parameter ALARM_ENABLE = 0

The device will check the timer to reach the Cyclic_Data_Period to send the CYCLIC_DATA uplink message;


Please check the Payload document to understand clearly about uplink messages, downlink messages, meaning of parameters for configuration...

Principle of Operation of Sensor part (if available)

The very low current from the gas sensor is amplified by a special amplifier circuit to deliver stable and high resolution.


The special mechanism provides noise filtering so that it can deliver a very stable output. The ADC chip can provide a resolution from 16-bit to 24-bit.


The circuit will deliver the digital output to the reading device.


The Exd G sensor module will deliver 02 values:

  • Gas concentration, in ppm or ppb.

  • An optional temperature of the circuit board, in ℃.

Default Configuration Parameters of Sensor part (if available) 

This Ex d approved G gas sensor module has the default configuration, however, those parameters can be changed. The user can change the configuration on the wireless transmitter so that the complete sensor (transducer + wireless) delivers the proper output value. Please check the Payload document for more information

3.2 Configuration

How to configure the device?

Sensor configuration can be configured in 02 methods:

​Method 1: Configuring via Downlink messages, port 1 (default)


Method 2: Configuring via Offline cable.


Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.


Which Parameters are configured?

Please check Part G in Section 1.9 Payload Documents above.

Method 1: Configuration via Downlink messages

Please check the Part D & E in Section 1.9 Payload Documents above.

Method 2: Configuration by Offline Cable

Please download the Configuration Template File of this sensor to be used in Step 4 below.

Instructions for offline configuration of the Daviteq LoRaWAN sensors. Please follow the following steps.


Note: The sensor is only active for offline configuration in the first 60 since power up by battery or plugging the configuration cable.


1. Prepare equipment and tools

The following items must be prepared for configuration.

  • A PC using the Windows OS (Windows 7 or above versions). The PC installed the COM port driver of the Modbus configuration cable (if needed). The driver is at link: Modbus Configuration Cable COM port driver for PC and the instruction to install  the driver at link: How to install the driver.

  • A Modbus configuration cable 

  • Tools to open the plastic housing of LoRaWAN sensors (L hex key or screwdriver)


2. Download and launch Daviteq Modbus configuration software 

  • Click the link below to download Daviteq Modbus configuration software:

https://filerun.daviteq.com/wl/?id=yDOjE5d6kqFlGNVVlMdFg19Aad6aw0Hs

After downloading the software, unzip the file named: Daviteq Modbus Configuration.zip and then copy the extracted folder to the storage drive for long-term use. 

  • Open the folder, double click on the file Daviteq Modbus Configuration Tool Version.exe to launch the software and the software interface as below:


Note: The software only runs on Microsoft Windows OS (Windows 7 and above).


3. Connect the cable and configure the sensor

Step 1: 

Connect the PC to the sensor using the configuration cable.

- Use the configuration cable (Item code: TTL-LRW-USB-01).


- Connect the USB-A plug into the USB-A socket of the PC.


Step 2: 

On the configuration software, choose the relevant Port (the USB port which is the cable plugged in) and set the BaudRate: 9600, Parity: none


Step 3:

Click Connect button to connect the software to the sensor. After successful connection, the Connected status will show on the software.


Step 4: 

Import the configuration template file of the sensor (as above link) to the software: click menu File/ Import New and then browse the relevant sensor template file (csv file) and click Open to import the template file.


Note: The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor.

Each sensor type has its own template file. Refer to the sensor's manual to download the correct file.


Step 5:

Open the housing of the sensor and quickly plug the connector of the configuration cable into sensor's modbus configuration port as below figure. After plugging the connector, the software will read the parameter values automatically.


Plug the cable connector into sensor's modbus configuration port. This port is located at a different location, depends on the sensor type 


Note: If the sensor has SKU of WSLRWEX-PPS and hardware version 1 & 2, the sensor must be powered by batteries for configuration


Step 6: 

Read the current value of the parameter with Modbus Function 3

  • At the relevant row of the parameter, check box 3 on column Func to read the value of the parameter. The read value is shown in VALUE ON MEMMAP column.



The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.


Step 7: 

Write the new setting to the parameter with Modbus Function 16

  • Double click on the column VALUE TO WRITE of the parameter and input the new setting value of the parameter;

  • Uncheck the tick on the FC column of the parameter, click on the arrow, select 16 and then check on the FC column to write a new setting to the parameter. The WRITE_OK text will show on EXCEPTION column if the software successfully writes the setting.


Repeat Step 6 to read the setting of the parameter for double-checking.


Note: For some critical parameters of the sensor, the password in "password for setting" must be written before writing the new settings to these parameters.

Only read/ write registers are allowed to write.

The sensor is only active for configuration for 60 seconds since plugging the configuration cable or the power supply into the sensor. After 60 seconds, the TIME_OUT text will show on EXCEPTION column of the software.


4. Troubleshooting

3.3 Calibration/ Validation

How to force sensor to send data for calibration/ validation (if available)

By using the magnet key, the LoRaWAN device can be triggered to send data to the gateway immediately. There will be a beep sound from the buzzer meaning the data has been sent (Buzzer will be updated in the latest version).



Note:

Once sending data to the gateway by magnet key, the timer of sending time interval will be reset;

The shortest time interval between the two manual triggers is 15s. if shorter than 15s, there will be no data sending.



Calibration/ Validation sensor (if available)

The Daviteq Ex d G Gas Sensor must be connected to a reading device, normally it is a wireless transmitter like Sub-GHz, Sigfox, or LoRaWAN, or a wired transmitter with Modbus output, 4∼20mA output, 0∼10V output.


In the reading device, the following parameter is configured in advance:

  • Sensor + amplifier sensitivity (mV/ ppm): it is the voltage output of the amplifier circuit = Sensor current output (nA/ ppm) x R_gain


For example, with an NH3 gas sensor, the default value of the Sensor current output is 110nA/ ppm and R_gain = 100 kΩ.

Therefore, the default NH₃ Sensor + amplifier sensitivity = 11 mV/ ppm.


Depending on the sensor type and R_gain value, the sensor sensitivity must be calculated and pre-configured into the reading device.


Why do we need to calibrate the gas sensor? There are some reasons:

  • The sensor current output of a sensor is different from the other sensor. It is not the same value for all sensors after manufacturing.

  • The sensor current output of a sensor will be changed over time. For example, the NH₃ sensor current output will be reduced by about 5% of the signal per six months in clean air at 25℃ temperature. For the air with a high concentration of target gases, the sensor's sensitivity will be reduced quickly.

  • The R_gain of the circuit also has a 0.1% or 0.05% tolerance;

  • Therefore, users need to calibrate the sensor before use or in a pre-defined interval time (6 or 12 months for example).


How to calibrate the G Gas sensor?

Instructions to attach the calibration cap onto the sensor module to get Zero or Span values.


NOTE: THE CALIBRATION CAN ONLY BE DONE IN THE SAFE ZONE!!!


Please follow the steps for Instructions to attach the calibration cap to the sensor module to get Zero or Span values:


Step 1. Remove the Filter and prepare the calibration cap


Step 2. Attach the calibration cap to the sensor head


Step 3. Installed the Regulator to the Gas cylinder


Step 4. Attach the tube to the regulator

Please select the flow regulator with a flow rate of 2.5 LPM or 5.0 LPM.


With the 2-point calibration method, the user can define the A and B factors. Please find below the steps of calibration.


Step 1. Get the Zero value.

- Power ON the device;

- Place the device in a clean-air environment (the target value is nearly zero) at a temperature from 20∼30℃, in at least 60 minutes.

- After 60 minutes, force the device to send data, read and record the Raw_value, so now you got the Zero_value = Raw_value value.

Recommendation: Record many Raw_value values ​​at least 10 minutes apart (10 values). Zero value is the average of the recorded Raw values.


Note: The Raw_value values can be positive or negative;


Step 2. Get the Span value


Note: Keep the sensor Power ON all the time


- Use the standard gas cylinder with a known concentration (for example Eythylene Air  1.35% is equivalent to 50% LEL ) to supply the gas to the sensor;

- Use the calibration cap as above pictures to attach to the sensor and connect the tubing to the gas cylinder;

- Open the valve on the Cylinder slowly and make sure the gas has reached the sensor. The flow regulator should be 2.5 LPM or 5.0 LPM.


Notes: The tube length is short as possible to reduce the gas loss.


- Press a timer to start counting the time;

- After 2 minutes, force the device to send data once every minute, and stop forcing at 5 minutes;

- The highest Raw_value is the Span value.


Note: Just get one value for Span.


- After that, immediately turn OFF the valve to save the gas;

- Remove the calibration cap from the sensor;

- Place the sensor in clean air again.


Note: Always keep the sensor Power ON all the time.


Step 3. Calculate the new A and B

The calculation of new A, B value based on basic linear formula:

y = A * x + B

Where:

A, B is calibration coefficients

x is the sensor process value (example gas level in ppm) read on reading device such as on application server/network server, on offline tool. The process value is the RAW_VALUE in the payload

y is the correct value. y is the value of standard gas/standard condition


Which condition of Zero value: y₀ = A * x₀ + B

Which condition of Span value: yₛ = A * xₛ+ B


From the two formulas, the calculation of A, B as below

A = (y₀ - yₛ) / (x₀ - xₛ)

B = (yₛ * x₀ - y₀ * xₛ) / (x₀ - xₛ)


Example of A, B calculation for LoraWAN Ammonia Gas sensor (item code WSLRW-G4-NH3-100-01):

* With condition of clean-air environment at a temperature from 20∼30℃, there is no ammonia gas (y₀ = 0); while the NH₃ level on reading device (RAW_VALUE in the payload) is -0.25 (x₀ = -0.25)

* When the sensor is connected to standard gas cylinder having ammonia level of 25 ppm (yₛ = 25); while the NH₃ level on reading device (RAW_VALUE in the payload) is 18.66 (xₛ = 18.66)


The calculation of A, B for the Ammonia gas sensor:          

A = (0 - 25) / (-0.25 - 18.66) = 1.32205

B = (yₛ * x₀ - y₀ * xₛ) / (x₀ - xₛ) = (25 * (-0.25) - 0 * 18.66) / (-0.25 - 18.66) = 0.33051


The factory default A = 1 and default B = 0


The RAW_VALUE in the payload is used for calibration


Step 4. Configure the new A and B into the device

- User can use the off-line tool or downlink to write the values of A and B;

- Writing the new A and B successfully meant you had done the calibration process. Congratulation!

4
PRODUCT SPECIFICATIONS

4.1 Specifications

Measurement technologyDaviteq High-performance Ultra-low power Electro-chemical Gas Sensor
Select Gas Sensor typeCO, NO, NO₂, H₂S, NH₃, O₂, O₃, SO₂, Cl₂, HCHO etc.
Gas sensor type and specificationList of compatible gas sensors and specification
COMMUNICATION
SF FactorsSF7∼SF12
AntennaExternal Antenna 2.0dbi
RF Frequency and Power860∼930MHz, 14∼20dBm, configurable for zones: EU868, IN865, RU864, KR920, AS923, AS923-2, AU915, US915
ProtocolLoRaWAN® Class A
Data sending modesinterval time, an alarm occurred and manually triggered by a magnetic key. Recommend max 24 messages per day
Configurationvia Downlink or offline USB cable (PC software is supplied for free)
Battery01 type C 3.6V LiSOCl₂ battery (recommended SAFT LS26500)
HousingAluminum alloy, powder coated, IP66, Wall mount installation
Certified Ex dIMQ 14 ATEX 005 X, TÜV CY 18 ATEX 0206158 X and SIRA 10ATEX1358X
Hazard Protection LabelATEX II 2G Ex db IIC T5/T6 Gb, ATEX II 2G Ex db mb [ia Ga] IIA/IIB/IIC T5..T6 Gb, and ATEX II 2 G Ex d IIC T4 Gb
CompatibleATEX 2014/34/EU/ Standard IEC-EN60079-0 IEC-EN60079-1 IEC-EN60079-31
Areas of applicationZones 1 & 2 gas hazardous areas
Size | Net weight H220xW100xD80 (not including antenna)/ ≈1500g (without battery)
MountingWall mount bracket

5
WARRANTY & SUPPORT

5.1 Warranty

Warranty

Below terms and conditions are applied for products manufactured and supplied by Daviteq Technologies Inc.


Free Warranty Conditions

  1. The manufacturer undertakes to guarantee within 12 months from shipment date.

  2. Product failed due to defects in material or workmanship.

  3. Serial number, label, warranty stamp remains intact (not purged, detected, edited, scraped, tore, blurry, spotty, or pasted on top by certain items).

  4. During the warranty period, if any problem of damage occurs due to technical manufacturing, please notify our Support Center for free warranty consultancy. Unauthorized treatments and modifications are not allowed.

  5. Product failed due to the defects from the manufacturer, depending on the actual situation, Daviteq will consider replacement or repairs.


Note: One way shipping cost to the Return center shall be paid by Customers.


Paid Warranty

  1. The warranty period has expired.

  2. The product is not manufactured by Daviteq.

  3. Product failed due to damage caused by disasters such as fire, flood, lightning or explosion, etc.

  4. Product damaged during shipment.

  5. Product damaged due to faulty installation, usage, or power supply.

  6. Product damage caused by the customer.

  7. Product rusted, stained by effects of the environment or due to vandalism, liquid (acids, chemicals, etc.)

  8. Product damage is caused by unauthorized treatments and modifications.


Note: Customers will be subjected to all repairing expenses and 2-way shipping costs. If arises disagreement with the company's determining faults, both parties will have a third party inspection appraise such damage and its decision be and is the final decision.


5.2 Support

Support via Help center

If you need our support for Daviteq device's installation, configuration, test, and decode, please email us at: support@daviteq.com OR input support request at link: https://forms.office.com/r/XWHbYG7yy7

Our support engineer will contact you via email or the support ticket system.

 

If you have any questions about the product, you can search for information on our web (https://www.iot.daviteq.com/). If you can't find the right information, please register an account and send us a request at link Contact us | Daviteq Technologies . We will respond within 24 hours.

bottom of page